-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fix ICE in missing_const_for_fn
#14776
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The `mir_drops_elaborated_and_const_checked` query result has been stolen already and cannot be borrowed again. Use the `optimized_mir` query result instead.
@blyxyas I'm not setup to do perf checks right now, don't hesitate if you want to comment on this change. |
For what it's worth, this actually used to use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It happened. It really happened that #14003 caused an ICE. I did black magic to try and perform a top 800 lintcheck run on that PR and it was all for nothing. That PR got delayed like 2 months for nothing.
At least it was Matthias who found it and not a random user.
As soon as this is merged, it should probably be backported.
@y21 @blyxyas Feel free to merge it and beta-nominate it, I assigned Jarcho just because when we talked about MIR during the latest meeting he joked that he ended up with all the MIR related PRs. I'm not sure it deserves to be backported to stable even if there is a 1.87.1, as this is a nursery lint, and seems to only trigger with |
In fact the ICE hadn't entered 1.87 since #14003 was merged some days after the last Clippy sync preceding the 1.87 beta branch creation. Backporting to beta will be enough indeed. |
The
mir_drops_elaborated_and_const_checked
query result has been stolen already and cannot be borrowed again. Use theoptimized_mir
query result instead.changelog: [
missing_const_for_fn
]: fix ICE with some compilation optionsFixes #14774
r? @Jarcho